Aircraft information management system

ABSTRACT

A method and apparatus comprising an existing aircraft node and an information agent located in the existing aircraft node. The existing aircraft node is connected to a number of aircraft systems and a network in an aircraft network data processing system. The information agent is configured to provide access to information received by the existing aircraft node to other aircraft nodes in the aircraft network data processing system.

BACKGROUND INFORMATION

1. Field

The present disclosure relates generally to aircraft and, in particular,to managing information in aircraft. Still more particularly, thepresent disclosure relates to a method and apparatus for obtaininginformation from line replaceable units in an aircraft.

2. Background

Aircraft increasingly have more and more electrical systems that controlthe operation of the aircraft, monitor the operation of the aircraft,and provide other functions. These electrical systems may be nodes in anaircraft network data processing system. Oftentimes, these nodes areimplemented as line replaceable units. A line replaceable unit receivesinformation needed to perform operations through connections to variousdevices.

For example, a line replaceable unit in an environmental control systemmay have connections to temperature sensors, airflow sensors, carbondioxide sensors, vent actuators, cooling units, heating units, and otherdevices. The line replaceable unit may receive information from thedifferent sensors and control operation of the heating units, coolingunits, and vents to provide a desired environment within the aircraft.These different components are typically connected directly to the linereplaceable unit. These connections may be made using wires and databuses that are directly connected to a line replaceable unit.

Currently, if another line replaceable unit needs temperatureinformation from the same locations as the sensors for the first linereplaceable unit, additional sensors may be placed at those locationsand connected to the second line replaceable unit, or additionalconnections may be made between the second line replaceable unit and theexisting temperature sensors. The addition of new sensors or newconnections from additional sensors may require the routing of wiringthrough the aircraft. In existing aircraft, the ability to route newwiring may be limited and more costly than desired.

Adding additional sensors may increase the cost and weight of theaircraft more than desired. Connecting the second line replaceable unitto the temperature sensors using wires or optical fibers may alsoincrease the time and expense needed. Further, generating additionalcommunications links to the different sensors or components may takemore time than desired and increase the complexity of the aircraft morethan desired. Moreover, this increase in wires or optical fibers withinthe aircraft also may result in more maintenance than desired.

Therefore, it would be desirable to have a method and apparatus thattakes into account at least some of the issues discussed above, as wellas other possible issues.

SUMMARY

In one illustrative embodiment, an apparatus comprises an existingaircraft node and an information agent located in the existing aircraftnode. The existing aircraft node is connected to a number of aircraftsystems and a network in an aircraft network data processing system. Theinformation agent is configured to provide access to informationreceived by the existing aircraft node to other aircraft nodes in theaircraft network data processing system.

In another illustrative embodiment, an apparatus comprises an aircraftnode and an information agent located in the aircraft node. The aircraftnode is configured to be located in an aircraft and communicate with anumber of aircraft systems in the aircraft. The information agent isconfigured to identify information received from the number of aircraftsystems that correspond to a subscription for an application in a hostaircraft node in the aircraft and send the information identified to theapplication in the host aircraft node.

In yet another illustrative embodiment, an information management systemcomprises an aircraft node, a host aircraft node, an information agentin the aircraft node, and a manager located in the host aircraft node.The aircraft node is configured to be located in an aircraft andcommunicate with a number of aircraft systems in the aircraft. The hostaircraft node is configured to communicate with the aircraft node. Theinformation agent is configured to identify information received fromthe number of aircraft systems that correspond to a request from thehost aircraft node in the aircraft and send the information identifiedto the host aircraft node. The manager is configured to process theinformation received from the information agent from the aircraft nodeand process the information received from the aircraft node.

In yet another illustrative embodiment, a method for collectinginformation in an aircraft is present. Information received from anumber of aircraft systems at an aircraft node is identified using anumber of connections to the number of aircraft systems. The informationidentified is requested information that is requested by an applicationin a host aircraft node. The requested information is sent to theapplication in the host aircraft node.

The features and functions can be achieved independently in variousembodiments of the present disclosure or may be combined in yet otherembodiments in which further details can be seen with reference to thefollowing description and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features believed characteristic of the illustrativeembodiments are set forth in the appended claims. The illustrativeembodiments, however, as well as a preferred mode of use, furtherobjectives and features thereof, will best be understood by reference tothe following detailed description of an illustrative embodiment of thepresent disclosure when read in conjunction with the accompanyingdrawings, wherein:

FIG. 1 is an illustration of an aircraft in accordance with anillustrative embodiment;

FIG. 2 is an illustration of a block diagram of an informationenvironment in accordance with an illustrative embodiment;

FIG. 3 is an illustration of a block diagram of an informationmanagement system in accordance with an illustrative embodiment;

FIG. 4 is an illustration of a block diagram of an entry in a systemdatabase in accordance with an illustrative embodiment;

FIG. 5 is an illustration of a block diagram of a subscription inaccordance with an illustrative embodiment;

FIG. 6 is an illustration of a flowchart of a process for collectinginformation in accordance with an illustrative embodiment;

FIG. 7 is an illustration of a flowchart of a process for processingrequests from applications in accordance with an illustrativeembodiment;

FIG. 8 is an illustration of a flowchart of a process for receivinginformation in accordance with an illustrative embodiment;

FIG. 9 is an illustration of a flowchart of a process for establishing asubscription in accordance with an illustrative embodiment;

FIG. 10 is an illustration of a flowchart of a process for identifyinginformation for an application in accordance with an illustrativeembodiment; and

FIG. 11 is an illustration of a data processing system in accordancewith an illustrative embodiment.

DETAILED DESCRIPTION

The illustrative embodiments recognize and take into account one or moredifferent considerations. For example, the illustrative embodimentsrecognize and take into account that one solution may be to connectnodes, such as line replaceable units, and the other devices in thedifferent aircraft systems to a network. For example, a set of sensorsmay be connected to the network. If a line replaceable unit that is notdirectly connected to a set of sensors needs information from thosesensors, that information may be obtained from the set of sensorsthrough the network.

The illustrative embodiments take into account that this solution may beuseful in designing and building new aircraft. However, with existingaircraft, changing existing connections between line replaceable unitsand other devices in the aircraft may be more time consuming, morecomplex, and more difficult than desired. These connections are physicalconnections using physical links such as wires and optical fibers.

For example, access to install new wiring and space for new wiring maybe limited or unavailable in the aircraft. As a result, the currentlyused point-to-point connections between line replaceable units andexisting aircraft systems may be more limited than desired.

As a result, obtaining information from an existing aircraft systemrequires making a new connection between the existing aircraft systemand the line replaceable unit in which the information is desired.Establishing a connection is often more difficult than desired. Whenlimited access is present, numerous components may need to be removed toprovide the access needed to make the new connection.

In some cases, access to make the new connection may be infeasible.Consequently, information desired for use in a line replaceable unit notalready connected to the existing aircraft system may be unavailablewhen a new connection cannot be made.

Thus, the illustrative embodiments recognize and take into account thatwhen a line replaceable unit or an application in a line replaceableunit needs information from an existing aircraft system, making a newconnection to a line replaceable unit or connecting the existingaircraft system to a network may be more difficult than desired.

Instead, the illustrative embodiments recognize and take into accountthat the different line replaceable units may be connected to each otheror another node directly or through a network to which the linereplaceable units are connected. These connections may be easier to makecompared to making a new connection to an existing aircraft system fromwhich information is desired. The line replaceable unit with theexisting connection to the aircraft system may be configured to sendinformation that is desired from the existing aircraft system to theline replaceable unit in which the information is desired.

The illustrative embodiments recognize and take into account thatinformation collected by the line replaceable unit using existingconnections may be sent to another node for processing using a functionincluded in the line replaceable unit. For example, if a second linereplaceable unit needs information from the sensors connected to a firstline replaceable unit, that information may be gathered by the firstline replaceable unit and sent to the second line replaceable unit. Thisinformation is already gathered by the first line replaceable unit aspart of its existing functionality. Therefore, existing connections donot need to be changed. As a result, the time and complexity ofupgrading or changing nodes in an aircraft may be reduced.

With reference now to the figures, and in particular, with reference toFIG. 1, an illustration of an aircraft is depicted in accordance with anillustrative embodiment. In this illustrative example, aircraft 100 haswing 102 and wing 104 attached to body 106. Aircraft 100 includes engine108 attached to wing 102 and engine 110 attached to wing 104.

Body 106 has tail section 114. Horizontal stabilizer 116, horizontalstabilizer 118, and vertical stabilizer 120 are attached to tail section114 of body 106.

Aircraft 100 is an example of an aircraft in which an aircraft networkdata processing system may be implemented with an information managementsystem in accordance with an illustrative embodiment. The informationmanagement system may be used to obtain information from aircraftsystems that are not directly connected to the aircraft network dataprocessing system.

With reference now to FIG. 2, an illustration of a block diagram of aninformation environment is depicted in accordance with an illustrativeembodiment. As depicted, information environment 200 is an example of aninformation environment that may be implemented within aircraft 100 inFIG. 1.

As depicted, information environment 200 includes aircraft network dataprocessing system 202. Aircraft network data processing system 202includes network 204 and aircraft nodes 206.

Network 204 is a medium used to provide communications between aircraftnodes 206 in aircraft network data processing system 202. Network 204may include connections such as wired communications links, wirelesscommunications links, optical communications links, and other suitabletypes of connections.

Aircraft nodes 206 are hardware devices. Aircraft nodes 206 areconfigured to process information. Additionally, aircraft nodes 206 alsomay control operation of aircraft systems 208. These nodes may be, forexample, without limitation, computers, processor units, controllers, orother suitable devices.

Aircraft systems 208 may take various forms. For example, withoutlimitation, aircraft systems 208 may be at least one of a sensor system,a flight recorder, a navigation system, a flight control system, anenvironmental control system, an engine system, or some other suitabletype of system.

As used herein, the phrase “at least one of”, when used with a list ofitems, means different combinations of one or more of the listed itemsmay be used and only one of each item in the list may be needed. Forexample, “at least one of item A, item B, and item C” may include,without limitation, item A or item A and item B. This example also mayinclude item A, item B, and item C, or item B and item C. In otherexamples, “at least one of” may be, for example, without limitation, twoof item A, one of item B, and ten of item C; four of item B and seven ofitem C; and other suitable combinations.

In these illustrative examples, aircraft nodes 206 take the form of linereplaceable units 210. A line replaceable unit in line replaceable units210 is a modular component that is designed to be quickly replaced atthe location of the line replaceable unit. A line replaceable unit istypically sealed in a housing. In these illustrative examples, linereplaceable units 210 may include computers, processor units,controllers, and other suitable types of devices.

As depicted, one or more of aircraft nodes 206 may be connected toaircraft systems 208 through connections 212. Connections 212 areconnections outside of network 204 in these illustrative examples. Inother words, aircraft systems 208 are not “networked” as part ofaircraft network data processing system 202. In some illustrativeexamples, connections 212 may be referred to as direct connectionsbecause aircraft systems 208 may be directly connected to one or more ofaircraft nodes 206 using wires, optical fibers, or some combinationthereof.

Connections 212 may be, for example, wires in data buses that carryanalog signals. These wires are physically routed to one or more ofaircraft nodes 206.

In these illustrative examples, information management system 214 may beused to obtain information 216 from a number of aircraft systems 208. Asused herein, a “number of” when used with reference to items means oneor more items. For example, a number of aircraft systems 208 is one ormore aircraft systems.

In this illustrative example, information management system 214comprises aircraft node 218 in aircraft nodes 206 and host aircraft node220. Aircraft node 218 is connected to a number of aircraft systems 208and network 204. Host aircraft node 220 may be a node in aircraft nodes206 in these illustrative examples. Host aircraft node 220 is connectedto network 204.

As depicted, applications 222 run on host aircraft node 220. Theseapplications take the form of software, hardware, or a combination ofthe two. An application may perform various functions that requireinformation 216 from a number of aircraft systems 208. Host aircraftnode 220, however, does not have a connection to the number of aircraftsystems 208 from which information 216 is obtained through network 204.

In these illustrative examples, information agent 224 is located inaircraft node 218. Information agent 224 is a function, process or somecombination thereof that may be implemented in software, hardware or acombination of the two. Information agent 224 communicates using network204.

Information agent 224 is configured to provide access to information 216received by aircraft node 218 to other aircraft nodes in aircraft nodes206 in aircraft network data processing system 202. In theseillustrative examples, information agent 224 provides a pass-throughfunction for information 216. In other words, information 216 may besent to host aircraft node 220 for use by one or more of applications222 in addition to being processed or otherwise used by aircraft node218.

Information agent 224 responds to requests originated by applications222 for information 216 that is needed by a number of applications 222running on host aircraft node 220. Information agent 224 may collectinformation 216 and send information 216 to applications 222 on hostaircraft node 220.

As a result, information 216 may be used both by aircraft node 218 andby a number of applications 222. This use of information 216 occurswithout needing additional connections in connections 212 from hostaircraft node 220 to number of aircraft systems 208. Further,information 216 may be obtained without connecting aircraft systems 208to network 204 in these illustrative examples. Further, information 216obtained may be changed over time through applications 222 sending newrequests to information agent 224. The change in information 216 may beperformed without modification to connections to number of aircraftsystems 208. In other words, additional connections to number ofaircraft systems 208 are not needed.

In this manner, information agents may be used within aircraft nodes 206to provide other aircraft nodes in aircraft nodes 206 with access toinformation from aircraft systems 208 connected to those other aircraftnodes. In these illustrative examples, the aircraft nodes in aircraftnodes 206 that have connections 212 to aircraft systems 208 may beexisting aircraft nodes. As a result, the aircraft nodes in aircraftnodes 206 with information agents may act as access points for obtaininginformation 216 from aircraft systems 208.

Turning now to FIG. 3, an illustration of a block diagram of aninformation management system is depicted in accordance with anillustrative embodiment. Information management system 300 in FIG. 3 isan example of one implementation for information management system 214in FIG. 2.

As depicted, information management system 300 includes host linereplaceable unit 302 and existing line replaceable unit 304. Host linereplaceable unit 302 is an example of host aircraft node 220 in FIG. 2.Existing line replaceable unit 304 is an example of aircraft node 218 inFIG. 2. As depicted, manager 306 is located in host line replaceableunit 302 and information agent 308 is located in existing linereplaceable unit 304.

In these illustrative examples, applications 312 run on host linereplaceable unit 302. Applications 312 may take a number of differentforms. For example, applications 312 may be at least one of an enginevibration monitoring application, a maintenance application, a fuel useapplication, a health monitoring application, and other suitable typesof applications.

A number of applications 312 may require information 314 from a numberof aircraft systems 310. As depicted, aircraft systems 310 are connectedto existing line replaceable unit 304 and are in communication withexisting line replaceable unit 304.

Aircraft systems 310, however, are not in communication with host linereplaceable unit 302 in this illustrative example. As a result, hostline replaceable unit 302 is unable to obtain information 314 from thenumber of aircraft systems 310. In other words, a connection that allowsfor an exchange of data between number of aircraft systems 310 and hostline replaceable unit 302 is absent in this illustrative example.

In these illustrative examples, manager 306 and information agent 308communicate with each other to provide information 314 from the numberof aircraft systems 310 needed by applications 312. For example,information agent 308 is configured to respond to requests originatedfrom application 316 to identify information 314 received from thenumber of aircraft systems 310 for application 316 in applications 312in host line replaceable unit 302. Information 314 is identified byinformation agent 308 using subscription 318 application 316.Subscription 318 originates from requests generated by application 316.

When information 314 is received from the number of aircraft systems 310and identified by information agent 308, information 314 is sent toapplication 316 in host line replaceable unit 302. In these illustrativeexamples, information agent 308 is configured to encrypt information 314before sending information 314 to application 316. In this manner,information 314 may be maintained as confidential and secure.

In another illustrative example, application 316 sends request 320 forinformation 314 to manager 306. Manager 306 uses system database 322 toidentify a source for information 314. In these illustrative examples,the source may be one or more nodes in the aircraft network dataprocessing system. In some illustrative examples, the node that is thesource for information 314, may be, for example, host line replaceableunit 302 itself. System database 322 is a database identifying differentnodes and aircraft systems connected to those nodes.

Using system database 322, manager 306 identifies existing linereplaceable unit 304 as a node having connections to the number ofaircraft systems 310 that are configured to supply information 314 thatis needed by application 316. In response to identifying existing linereplaceable unit 304, manager 306 communicates with information agent308 in existing line replaceable unit 304 to generate subscription 318.

Information agent 308 monitors information 324 received from number ofaircraft systems 310 over connections 325 for information 314 forapplication 316 using subscription 318 for application 316 in host linereplaceable unit 302. Connections 325 are direct connections betweenexisting line replaceable unit 304 and aircraft systems 310 in theseillustrative examples. As depicted, information 324 is information usedby existing line replaceable unit 304 to perform various functionswithin an aircraft.

When information 314 is identified in information 324, information 314is placed into data buffer 326 in existing line replaceable unit 304.Information 314 is then transmitted from data buffer 326 to manager 306in host line replaceable unit 302 over network connection 328. In theseillustrative examples, network connection 328 may be comprised of one ormore communications links within network 204 in FIG. 2. Information 314is then sent to application 316.

In this illustrative example, information 314 may be sent to application316 by manager 306 through data buffer 330. For example, information 314may be placed in data buffer 330, and application 316 may retrieveinformation 314 from data buffer 330. Data buffer 330 is a data bufferassociated with application 316. Although the illustrative examples usea data buffer, other types of storage or other types of mechanisms maybe used in addition to or in place of data buffer 330 to sendinformation 314 to application 316.

In these illustrative examples, each application in applications 312requesting information may have a separate data buffer. Alternatively,data buffer 330 may be common to all of applications 312 with eachapplication looking for information in specific address ranges.

In some illustrative examples, a portion or all of information 314requested by application 316 may be obtained locally through host linereplaceable unit 302. For example, host line replaceable unit 302 may beconnected to aircraft system 332. In this case, if information 314identified by request 320 is available from aircraft system 332, manager306 may generate subscription 334 to identify when information 314 isreceived from aircraft system 332. In this case, information 314 may beplaced in data buffer 330 by manager 306 when received from aircraftsystem 332.

Additionally, information 314 also may be transmitted to application 336located on node 338. In this illustrative example, node 338 may be acomputer, a tablet computer, a laptop, or some other device locatedoutside of an aircraft network data processing system. In other words,node 338 is not normally connected to the aircraft network dataprocessing system. Node 338 may communicate with host line replaceableunit 302 over wireless connection 340.

In this illustrative example, information 314 may be placed into a databuffer assigned to application 336. Manager 306 may transmit information314 found in the buffer to application 336 in node 338 over wirelessconnection 340.

Further, application 316 may make additional requests for information asthe need for information changes. Additionally, other applications inapplications 312 also may generate requests for information.

Turning now to FIG. 4, an illustration of a block diagram of an entry ina system database is depicted in accordance with an illustrativeembodiment. In this illustrative example, entry 400 is an example of anentry in system database 322 in FIG. 3. In this illustrative example,entry 400 includes fields for type of information 402, aircraft system404, and node 406.

The field for type of information 402 identifies what type ofinformation is to be obtained for an application. Type of information402 may be, for example, without limitation, fuel use, temperature,pressure, engine temperature, cabin temperature, outside temperature,control surface position, and other suitable types of information.

Type of information 402 also may include meta data that describes othertypes of information. The meta data may be, for example, resolution,calculation rate, transmission rate, and other suitable types ofinformation. This meta data may be used by application 312 and manager306 to determine which source of data should be used if more than one isavailable. Of course, type of information 402 may identify more than oneaircraft system in these illustrative examples.

The field for aircraft system 404 identifies the aircraft system thatprovides the desired type of information. For example, withoutlimitation, aircraft system 404 may be selected from one of a sensorsystem, a flight recorder, a navigation system, a flight control system,an environmental control system, an engine system, or some othersuitable type of system. Of course, aircraft system 404 may identifymore than one aircraft system in these illustrative examples.

The field for node 406 identifies a node connected to the aircraftsystem identified by aircraft system 404. This identification in node406 may be, for example, without limitation, an Internet Protocol (IP)address, an alphanumeric designation, or some other suitable type ofidentifier. In some illustrative examples, node 406 may be actually partof aircraft system 404 and connected to various components that providetype of information 402.

Thus, when type of information 402 is requested from an application,node 406 in entry 400 identifies a node in an aircraft network dataprocessing system from which information may be obtained. In theseillustrative examples, node 406 is a field that identifies a node inwhich an agent, such as information agent 224 in FIG. 2, is present.

Additionally, the request also may identify the aircraft system fromwhich type of information 402 is available. Thus, if type of information402 is available from more than one aircraft system, aircraft system 404in entry 400 may be used to identify which aircraft system should beused to obtain the information.

Of course, entry 400 may include other fields in addition to or in placeof the ones depicted in this figure. In other examples, aircraft system404 may be omitted.

Turning now to FIG. 5, an illustration of a block diagram of asubscription is depicted in accordance with an illustrative embodiment.Subscription 500 is an example of one manner in which subscription 318and subscription 334 in FIG. 3 may be implemented. As depicted,subscription 500 includes type of information 502, aircraft system 503,event 504, and application 506.

Type of information 502 identifies one or more types of information thatshould be sent for subscription 500. Event 504 identifies when type ofinformation 502 should be sent. For example, event 504 may be a periodicevent or a non-periodic event. In these illustrative examples, event 504may indicate that type of information 502 is to be collected and sentonly once.

In other illustrative examples, event 504 may indicate that type ofinformation 502 should be sent each time event 504 occurs. Event 504 maybe, for example, when a value for type of information 502 exceeds athreshold or has a particular value. For example, event 504 may indicatethat type of information 502 should be sent every five seconds, everyhour, or after some other periodic event.

In other illustrative examples, event 504 may indicate that type ofinformation 502 should be streamed constantly as type of information 502is received. In this case, information 314 is placed in data buffer 326for transmission to manager 306 as information 314 is received fromaircraft systems 310.

The illustration of subscription 500 in FIG. 5 is not meant to limit themanner in which a subscription may be implemented. Other types ofinformation may be included in addition to or in place of the types ofinformation illustrated in subscription 500. For example, subscription500 may include an identification of one or more aircraft systems fromwhich information should be collected and sent to an application. Theidentification of the aircraft system may be used in addition to or inplace of subscription 500.

The illustrations of information environment 200 in FIG. 2, informationmanagement system 300 in FIG. 3, and other components in FIGS. 2-5 arenot meant to imply physical or architectural limitations to the mannerin which an illustrative embodiment may be implemented. Other componentsin addition to or in place of the ones illustrated may be used. Somecomponents may be unnecessary. Also, the blocks are presented toillustrate some functional components. One or more of these blocks maybe combined, divided, or combined and divided into different blocks whenimplemented in an illustrative embodiment.

For example, one or more host nodes in addition to host aircraft node220 may be present in aircraft nodes 206. In still other illustrativeexamples, information management system 214 may be considered to includeinformation agent 224 and host aircraft node 220. In still otherillustrative examples, information management system 300 may beconsidered to include manager 306 and information agent 308 and notinclude host line replaceable unit 302 and existing line replaceableunit 304.

In still other illustrative examples, application 316 may include anidentification of type of information 402 and node 406 in request 320 tomanager 306. With this example, system database 322 may be unnecessary.

As another illustrative example, network 204 may be a single connectionbetween aircraft node 218 and host aircraft node 220. As anotherexample, network connection 328 between existing line replaceable unit304 and host line replaceable unit 302 may be a communications link suchas a wire, an optical fiber, or a wireless medium.

In some illustrative examples, connections 212 may be existingconnections between aircraft systems 208 and aircraft node 218. Aircraftnode 218 in aircraft nodes 206 may be an existing aircraft node to whichaircraft systems 208 are connected. In other words, the existingaircraft nodes and the existing connections may already be presentbefore information agent 224 is implemented in the existing aircraftnodes. In other illustrative examples, information agent 224 may beimplemented at substantially the same time as aircraft network dataprocessing system 202 and aircraft systems 208 for a new aircraft. Inother words, information management system 214 may be implemented suchthat large changes to the design of an aircraft, such as connectingaircraft systems 208 to network 204, may be avoided.

With reference now to FIG. 6, an illustration of a flowchart of aprocess for collecting information is depicted in accordance with anillustrative embodiment. In this depicted example, the differentoperations may be implemented in information management system 214 inFIG. 2 and information management system 300 in FIG. 3.

The process begins by identifying information received from a number ofaircraft systems at an aircraft node using a number of connections tothe number of aircraft systems (operation 600). In operation 600, theinformation identified is requested information that is requested by anapplication in a host aircraft node.

The process then sends the requested information to the application onthe host aircraft node (operation 602) with the process terminatingthereafter. The requested information is sent to the application in thehost aircraft node using a network in an aircraft network dataprocessing system. In these illustrative examples, operation 600 andoperation 602 may be implemented in an information agent in theinformation management system. In this manner, the information agent maycause the aircraft node to function as an access point for otheraircraft nodes.

With reference now to FIG. 7, an illustration of a flowchart of aprocess for processing requests from applications is depicted inaccordance with an illustrative embodiment. The process illustrated inFIG. 7 may be implemented in a host node, such as host aircraft node 220in FIG. 2 or host line replaceable unit 302 in FIG. 3. In theseillustrative examples, one or more of the operations may be implementedin manager 306 in FIG. 3.

The process begins by receiving a request for information from anapplication (operation 700). The process then determines whether theinformation requested can be obtained locally (operation 702). Thisdetermination may be made using system database 322 in FIG. 3. If theinformation cannot be obtained locally, the process requests theinformation from the remote source (operation 704) with the processterminating thereafter.

With reference again to operation 702, if the information can beobtained locally, the process generates a subscription for theinformation (operation 706) with the process terminating thereafter.This subscription may be used by the process to identify desiredinformation requested by the application as information is received fromone or more aircraft systems connected to the node on which this processruns.

Turning now to FIG. 8, an illustration of a flowchart of a process forreceiving information is depicted in accordance with an illustrativeembodiment. The process illustrated in FIG. 8 may be implemented in amanager, such as manager 306 in FIG. 3.

The process begins by receiving information (operation 800). Thisinformation may be received either over a network connection from aninformation agent or locally from aircraft systems. The processidentifies an application for the information received (operation 802).In this illustrative example, the identification of the application maybe included in the information received. The information agent sendingthe information may include an identifier for the application that is toreceive the information. The process then places the data into a bufferfor the application (operation 804) with the process terminatingthereafter.

Turning now to FIG. 9, an illustration of a flowchart of a process forestablishing a subscription is depicted in accordance with anillustrative embodiment. The process illustrated in FIG. 9 may beimplemented in an aircraft node, such as aircraft node 218 in FIG. 2, orexisting line replaceable unit 304 in FIG. 3. In particular, thisprocess may be implemented using information agent 308 to establish asubscription. In some cases, one or more of the operations in FIG. 9 maybe implemented in manager 306 to establish subscriptions for informationthat may be obtained locally. In this illustrative example, informationmay be obtained locally when the information is obtained from anaircraft system connected to the aircraft node on which the manager islocated.

The process begins by receiving a request for information (operation900). This request may include an identification of the type ofinformation. The process then creates a subscription based on therequest (operation 902) with the process terminating thereafter.

Turning now to FIG. 10, an illustration of a flowchart of a process foridentifying information for an application is depicted in accordancewith an illustrative embodiment. The process illustrated in FIG. 10 maybe implemented in information agent 308 in FIG. 3, manager 306 in FIG.3, or both.

The process begins by identifying information received from an aircraftsystem (operation 1000). Thereafter, the process determines whether theinformation should be sent to an application (operation 1002). Thisdetermination may be made by using the subscriptions generated fromrequests received from applications.

If the information should be sent to the application, the process thensends the information to a manager over a network connection (operation1004) with the process returning to operation 1000. When sendinginformation in operation 1004, a time stamp may be added to theinformation. The time stamp may be used to process data from differentsources. For example, the time stamp may be used to sort or organizeinformation received at different times from different sources.

In these illustrative examples, operation 1004 may include associatingthe information with the application. This association may be madethrough the use of an identifier or other indicator that may be includedwith, or sent in association with, the information identified for theapplication. With reference again to operation 1002, if the informationshould not be sent to the application, the process returns to operation1000.

The flowcharts and block diagrams in the different depicted embodimentsillustrate the architecture, functionality, and operation of somepossible implementations of apparatus and methods in an illustrativeembodiment. In this regard, each block in the flowcharts or blockdiagrams may represent a module, segment, function, and/or a portion ofan operation or step. For example, one or more of the blocks may beimplemented as program code, in hardware, or a combination of theprogram code and hardware. When implemented in hardware, the hardwaremay, for example, take the form of integrated circuits that aremanufactured or configured to perform one or more operations in theflowcharts or block diagrams.

In some alternative implementations of an illustrative embodiment, thefunction or functions noted in the blocks may occur out of the ordernoted in the figures. For example, in some cases, two blocks shown insuccession may be executed substantially concurrently, or the blocks maysometimes be performed in the reverse order, depending upon thefunctionality involved. Also, other blocks may be added in addition tothe illustrated blocks in a flowchart or block diagram.

Turning now to FIG. 11, an illustration of a data processing system isdepicted in accordance with an illustrative embodiment. Data processingsystem 1100 may be used to implement one or more of aircraft nodes 206in FIG. 2. Data processing system 1100 may be used to implement linereplaceable units 210 in FIG. 2. Additionally, data processing system1100 also may be used to implement host line replaceable unit 302 andexisting line replaceable unit 304 in FIG. 3. In this illustrativeexample, data processing system 1100 includes communications framework1102, which provides communications between processor unit 1104, memory1106, persistent storage 1108, communications unit 1110, input/output(I/O) unit 1112, and display 1114. In this example, communicationframework may take the form of a bus system.

Processor unit 1104 serves to execute instructions for software that maybe loaded into memory 1106. Processor unit 1104 may be a number ofprocessors, a multi-processor core, or some other type of processor,depending on the particular implementation.

Memory 1106 and persistent storage 1108 are examples of storage devices1116. A storage device is any piece of hardware that is capable ofstoring information, such as, for example, without limitation, data,program code in functional form, and/or other suitable informationeither on a temporary basis and/or a permanent basis. Storage devices1116 may also be referred to as computer readable storage devices inthese illustrative examples. Memory 1106, in these examples, may be, forexample, a random access memory or any other suitable volatile ornon-volatile storage device. Persistent storage 1108 may take variousforms, depending on the particular implementation.

For example, persistent storage 1108 may contain one or more componentsor devices. For example, persistent storage 1108 may be a hard drive, aflash memory, a rewritable optical disk, a rewritable magnetic tape, orsome combination of the above. The media used by persistent storage 1108also may be removable. For example, a removable hard drive may be usedfor persistent storage 1108.

Communications unit 1110, in these illustrative examples, provides forcommunications with other data processing systems or devices. In theseillustrative examples, communications unit 1110 is a network interfacecard.

Input/output unit 1112 allows for input and output of data with otherdevices that may be connected to data processing system 1100. Forexample, input/output unit 1112 may provide a connection for user inputthrough a keyboard, a mouse, and/or some other suitable input device.Further, input/output unit 1112 may send output to a printer. Display1114 provides a mechanism to display information to a user.

Instructions for the operating system, applications, and/or programs maybe located in storage devices 1116, which are in communication withprocessor unit 1104 through communications framework 1102. The processesof the different embodiments may be performed by processor unit 1104using computer-implemented instructions, which may be located in amemory, such as memory 1106.

These instructions are referred to as program code, computer usableprogram code, or computer readable program code that may be read andexecuted by a processor in processor unit 1104. The program code in thedifferent embodiments may be embodied on different physical or computerreadable storage media, such as memory 1106 or persistent storage 1108.

Program code 1118 is located in a functional form on computer readablemedia 1120 that is selectively removable and may be loaded onto ortransferred to data processing system 1100 for execution by processorunit 1104. Program code 1118 and computer readable media 1120 formcomputer program product 1122 in these illustrative examples. In oneexample, computer readable media 1120 may be computer readable storagemedia 1124 or computer readable signal media 1126.

In these illustrative examples, computer readable storage media 1124 isa physical or tangible storage device used to store program code 1118rather than a medium that propagates or transmits program code 1118.

Alternatively, program code 1118 may be transferred to data processingsystem 1100 using computer readable signal media 1126. Computer readablesignal media 1126 may be, for example, a propagated data signalcontaining program code 1118. For example, computer readable signalmedia 1126 may be an electromagnetic signal, an optical signal, and/orany other suitable type of signal. These signals may be transmitted overcommunications links, such as wireless communications links, opticalfiber cable, coaxial cable, a wire, and/or any other suitable type ofcommunications link.

The different components illustrated for data processing system 1100 arenot meant to provide architectural limitations to the manner in whichdifferent embodiments may be implemented. The different illustrativeembodiments may be implemented in a data processing system includingcomponents in addition to and/or in place of those illustrated for dataprocessing system 1100. Other components shown in FIG. 11 can be variedfrom the illustrative examples shown. The different embodiments may beimplemented using any hardware device or system capable of runningprogram code 1118.

Thus, the illustrative embodiments provide a method and apparatus foraccessing information from aircraft systems that are connected to nodes.In particular, the illustrative embodiments may be used to accessinformation received from aircraft systems by existing line replaceableunits.

The illustrative embodiments may configure existing line replaceableunits to act as access points for other nodes or line replaceable unitsfor information received from the aircraft systems. In theseillustrative examples, this access may be provided through the use of aninformation agent on an existing line replaceable unit.

In this manner, additional functionality may be added to existingaircraft through the use of information management system 214. Further,fewer changes to designs for aircraft may be made by adding informationmanagement system 214 to provide access to information generated byaircraft systems. For example, the aircraft systems may not need to beredesigned to be connected to an aircraft network data processingsystem.

The description of the different illustrative embodiments has beenpresented for purposes of illustration and description, and is notintended to be exhaustive or limited to the embodiments in the formdisclosed. Many modifications and variations will be apparent to thoseof ordinary skill in the art. Further, different illustrativeembodiments may provide different features as compared to otherdesirable embodiments. The embodiment or embodiments selected are chosenand described in order to best explain the principles of theembodiments, the practical application, and to enable others of ordinaryskill in the art to understand the disclosure for various embodimentswith various modifications as are suited to the particular usecontemplated.

1. An apparatus comprising: an existing node connected to a number ofsystems and a network in an network data processing system; and aninformation agent located in the existing node, wherein the informationagent is configured to provide access to information received by theexisting node to other nodes in the network data processing system. 2.The apparatus of claim 1, wherein in being configured to provide accessto the information received by the existing node to the other nodes inthe network data processing system, the information agent is configuredto identify the information received from the number of systems for anapplication using a subscription for the application in a host node inthe other nodes and send the information identified to the applicationin the host node.
 3. The apparatus of claim 2, wherein the subscriptionidentifies at least one of a type of information, an event, and theapplication.
 4. An apparatus comprising: an node configured to belocated in a vehicle and communicate with a number of systems in thevehicle; and an information agent located in the node, wherein theinformation agent is configured to identify information received fromthe number of systems that correspond to a subscription for anapplication in a host node in the vehicle and send the informationidentified to the application in the host node.
 5. The apparatus ofclaim 4 further comprising: the host node configured to receive theinformation from the node and send the information to the application.6. The apparatus of claim 5 further comprising: a manager located in thehost node, wherein the manager is configured to receive a request fromthe application in the host node, communicate with the information agentto generate the subscription, receive the information from theinformation agent, and send the information to the application.
 7. Theapparatus of claim 6, wherein in being configured to send theinformation to the application, the manager is configured to place theinformation into a data buffer for the application.
 8. The apparatus ofclaim 4, wherein the information agent is configured to encrypt theinformation.
 9. The apparatus of claim 4, wherein the subscriptionidentifies at least one of a type of information, an event, and theapplication.
 10. The apparatus of claim 4, wherein the node is a linereplaceable unit.
 11. The apparatus of claim 4, wherein a system in thenumber of systems is selected from one of a sensor system, a flightrecorder, a navigation system, a flight control system, an environmentalcontrol system, and an engine system.
 12. An information managementsystem comprising: an node configured to be located in a vehicle andcommunicate with a number of systems in the vehicle; a host nodeconfigured to communicate with the node; an information agent in thenode, wherein the information agent is configured to identifyinformation received from the number of systems that correspond to arequest from the host node in the vehicle and send the informationidentified to the host node; and a manager located in the host node,wherein the manager is configured to process the information receivedfrom the information agent from the node and process the informationreceived from the node.
 13. The information management system of claim12, wherein the information agent is configured to encrypt theinformation.
 14. The information management system of claim 12, whereinthe node is a line replaceable unit.
 15. The information managementsystem of claim 12, wherein an system in the number of systems isselected from one of a sensor system, a flight recorder, a flightcontrol system, an environmental control system, and an engine system.16. A method for collecting information in a vehicle, the methodcomprising: identifying the information received from a number ofsystems at an node using a number of connections to the number ofsystems, wherein the information identified is requested informationthat is requested by an application in a host node; and sending therequested information to the application in the host node.
 17. Themethod of claim 16, wherein sending the requested information to theapplication in the host node comprises: sending the requestedinformation to the application in the host node using a network in anetwork data processing system.
 18. The method of claim 16, wherein theidentifying step and the sending step are performed by an informationagent located in the node.
 19. The method of claim 18, wherein theinformation agent is configured to provide access to the informationreceived by the node to other nodes in a network data processing system.20. The method of claim 18, wherein the information agent identifies therequested information using a subscription for the application.